Incorporate JSONB elements and staging deployment #26
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Rename StatsRouter -> DefaultRouter * Enable CORS * Fix ChangesetCountry model / endpoint * Add support for JSONB columns * Make page sizes consistent * Make pagination 1-based * Make output formatting consistent (snake_case) * Output Timestamps as ISO-8601 strings (using Instants internally) * scalafmt
This will now produce the top 10 users / hashtags by number of edits. In addition, `user_edit_counts` (now `user_edits`) and `hashtag_edits` now surface number of edits (not changesets). Changeset counts are surfaced as `user_changesets` and `hashtag_changesets`.
Also, surface both changeset and edit counts per-user.
Also splits out changesets and edits for each dimension.
Update aggregation queries to use JSON columns
…paign-user-stats Staging deployments, railway stats, and campaign user stats
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR brings master into parity with current develop. These changes allow the stat server to use the new stat database schemas and separate staging and production deployments introduced in azavea/osmesa#157. This is in preparation for a deployment of the stat server into the production environment.